-
Notifications
You must be signed in to change notification settings - Fork 93
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Use roles from the embedded-cluster config #4133
Use roles from the embedded-cluster config #4133
Conversation
…he-admin-console-show-the-name-for-the
go 1.21.0 | ||
|
||
toolchain go1.21.3 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
this appears to be required as part of importing embedded-cluster-operator
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
would it make it an easier import if there was a separate module for the kinds/apis as we have for kotskinds and kurlkinds? probably not necessary now, but thinking ahead for when the project inevitably grows
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Might be something to consider certainly
…he-admin-console-show-the-name-for-the
if err != nil { | ||
return nil, fmt.Errorf("failed to list installations: %w", err) | ||
} | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
are there scenarios where the list returned could be empty?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There's an installation created with every embedded-cluster install, so ideally no
…he-admin-console-show-the-name-for-the
What this PR does / why we need it:
Includes the ability to specify custom node roles that include node labels when joining a node to the cluster.
I think no release notes as this is still in a pre-beta state
Which issue(s) this PR fixes:
Fixes #
Special notes for your reviewer:
Steps to reproduce
Does this PR introduce a user-facing change?
Does this PR require documentation?